home *** CD-ROM | disk | FTP | other *** search
- <html>
- <head>
- <title>Application Manifest</title>
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <link rel="stylesheet" type="text/css" href="help.css">
- </head>
- <table width="100%" border="0" bordercolor="#000000" bgcolor="#000000">
- <tr>
- <td bgcolor="#000000" height="19">
- <div align="left"><font face="Tahoma"><b><font size="4"> <font size="5" color="#FFFFFF">Application
- Manifest Resource </font></font></b></font></div>
- </td>
- </tr>
- </table>
- <p>An <b>Application Manifest</b> is an XML file that describes and identifies
- the shared and private side-by-side assemblies that an application should bind
- to at run time. More detailed information can be found on the <img src="extlink.gif" width="18" height="9">
- <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sbscs/sidebysideref_03ol.asp" target="_blank">Microsoft
- MSDN</a> site. </p>
- <p>The following is an example of an application manifest for an
- application named MySampleApp.exe. The application consumes the Common
- Controls side-by-side assembly (COMCTL32).</p>
- <PRE><?xml version="1.0"
- encoding="UTF-8" standalone="yes"?>
- <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
- <assemblyIdentity type="win32"
- name="myOrganization.myDivision.mySampleApp"
- version="6.0.0.0"
- processorArchitecture="x86"
- publicKeyToken="6595b64144ccf1df"
- />
- <description>Your app description here</description>
- <dependency>
- <dependentAssembly>
- <assemblyIdentity type="win32"
- name="Microsoft.Windows.Common-Controls"
- version="6.0.0.0"
- processorArchitecture="X86"
- publicKeyToken="6595b64144ccf1df"
- language="*"
- />
- </dependentAssembly>
- </dependency>
- </assembly></PRE>
- <p><b>Elements</b></p>
- <p>Names of elements and attributes are case-sensitive. The values of elements
- and attributes are case-insensitive, except for the value of the type attribute.
- <dl>
- <p><b>assembly</b>
- <p>A container element. Its first subelement must be a <b>noInherit</b> or
- <b>assemblyIdentity</b> element. Required.
- <p>The <b>assembly</b> element has the following attributes.
- <table>
- <tbody>
- <tr valign=top>
- <th align=left width="27%">
-
- <p><b>Attribute</b></p>
- </th>
- <th align=left width="73%">
-
- <p><b>Description</b></p>
- </th>
- </tr>
- <tr valign=top>
- <td width="27%">
- <p>manifestVersion</p>
- </td>
- <td width="73%">
- <p>The manifestVersion attribute must be set to 1.0.</p>
- </td>
- </tr>
- </tbody>
- </table>
- <br>
- <p></p>
- <p><b>noInherit</b>
- <dd>
- <p>Include this element in an application manifest to set the activation contexts
- generated from the manifest with the "no inherit" flag. When this flag is
- not set in an activation context, and the activation context is active,
- it is inherited by new threads in the same process, windows, window procedures,
- and Asynchronous Procedure Calls. Setting this flag prevents the new object
- from inheriting the active context.
- <p>The <b>noInherit</b> element is optional and typically omitted. Most assemblies
- do not work correctly using a no-inherit activation context because the
- assembly must be explicitly designed to manage the propagation of their
- own activation context. The use of the <b>noInherit</b> element requires
- that any dependent assemblies referenced by the application manifest have
- a <b>noInheritable</b> element in their assembly manifest.
- <p>If <b>noInherit</b> is used in a manifest, it must be the first subelement
- of the <b>assembly</b> element. The <b>assemblyIdentity</b> element should
- come immediately after the <b>noInherit</b> element. If <b>noInherit</b>
- is not used, <b>assemblyIdentity</b> must be the first subelement of the
- <b>assembly</b> element. The <b>noInherit</b> element has no child elements.
- It is not a valid element in assembly manifests. </p>
- <p><b>assemblyIdentity</b>
- <dd><p>As the first subelement of an <b>assembly</b> element, <b>assemblyIdentity</b>
- describes and uniquely identifies the application owning this application
- manifest. As the first subelement of a <b>dependentAssembly</b> element, <b>assemblyIdentity</b>
- describes a side-by-side assembly required by the application. Note that every
- assembly referenced in the application manifest requires an <b>assemblyidentity</b>
- that exactly matches the <b>assemblyIdentity</b> in the referenced assembly's
- own assembly manifest.
- <p>The element has the following attributes. It has no subelements.
- <table>
- <tbody>
- <tr valign=top>
- <th align=left width="24%">
- <p><b>Attribute</b></p>
- </th>
- <th align=left width="76%">
- <p><b>Description</b></p>
- </th>
- </tr>
- <tr valign=top>
- <td width="24%">
- <p>type</p>
- </td>
- <td width="76%">
- <p>Specifies the application or assembly type. The value must be win32
- and all in lower case. Required.</p>
- </td>
- </tr>
- <tr valign=top>
- <td width="24%">
- <p>name</p>
- </td>
- <td width="76%">
- <p>Uniquely names the application or assembly. Use the following format
- for the name: Organization.Division.Name. For example Microsoft.Windows.mysampleApp.
- Required.</p>
- </td>
- </tr>
- <tr valign=top>
- <td width="24%">
- <p>language</p>
- </td>
- <td width="76%">
- <p>Identifies the language of the application or assembly. Optional.
- If the application or assembly is language-specific, specify the DHTML
- language code. </p>
- <p>In the <b>assemblyIdentity</b> of an application intended for worldwide
- use (language neutral) omit the language attribute. </p>
- <p>In an <b>assemblyIdentity</b> of an assembly intended for worldwide
- use (language neutral) set the value of language to "*". </p>
- </td>
- </tr>
- <tr valign=top>
- <td width="24%">
- <p>processorArchitecture</p>
- </td>
- <td width="76%">
- <p>Specifies the processor. The valid values are x86 for 32-bit Windows
- and IA-64 for 64-bit Windows. Optional.</p>
- </td>
- </tr>
- <tr valign=top>
- <td width="24%">
- <p>version</p>
- </td>
- <td width="76%">
- <p>Specifies the application or assembly version. Use the four-part
- version format: mmmmm.nnnnn.ooooo.ppppp. Each of the parts separated
- by periods can be 0-65535 inclusive. Required.</p>
- </td>
- </tr>
- <tr valign=top>
- <td width="24%">
- <p>publicKeyToken</p>
- </td>
- <td width="76%">
- <p>A 16-character hexadecimal string representing the last 8 bytes of
- the SHA-1 hash of the public key under which the application or assembly
- is signed. The public key used to sign the catalog must be 2048 bits
- or greater. Required for all shared side-by-side assemblies.</p>
- </td>
- </tr>
- </tbody>
- </table>
- <br>
- <p></p>
- <p><b>dependency</b>
- <dd><p>Contains at least one <b>dependentAssembly</b>. It has no attributes. Optional.
- <p><b>dependentAssembly</b>
- <dd><p>The first subelement of <b>dependentAssembly</b> must be an <b>assemblyIdentity</b>
- element that describes a side-by-side assembly required by the application.
- Every <b>dependentAssembly</b> must be inside exactly one <b>dependency</b>.
- It has no attributes.
- <p><b>file</b>
- <dd><p>Specifies files that are private to the application. Optional.
- <p>The element has the attributes shown in the following table.
- <table>
- <tbody>
- <tr valign=top>
- <th align=left width="24%">
- <p><b>Attribute</b></p>
- </th>
- <th align=left width="76%">
- <p><b>Description</b></p>
- </th>
- </tr>
- <tr valign=top>
- <td width="24%">
- <p>name </p>
- </td>
- <td width="76%">
- <p>Name of the file. For example, Comctl32.dll.</p>
- </td>
- </tr>
- <tr valign=top>
- <td width="24%">
- <p>hashalg</p>
- </td>
- <td width="76%">
- <p>Algorithm used to create a hash of the file. This value should be
- SHA1.</p>
- </td>
- </tr>
- <tr valign=top>
- <td width="24%">
- <p>hash</p>
- </td>
- <td width="76%">
- <p>A hash of the file referred to by name. A hexadecimal string of length
- depending on the hash algorithm.</p>
- </td>
- </tr>
- </tbody>
- </table>
-
- </dd>
- </dl>
- <p> </p>
- <SCRIPT language="JavaScript" src="footer.js" type="text/javascript"></SCRIPT>
- </body>
- </html>
-